Collection of Internet/Collection of Internet.iso/infosrvr/dev/www_talk.930/[e-mail] _Tue Jun 1 18:34:07 1993.msg

Internet Message Format | 1994-01-24 | 2KB

Return-Path: <[e-mail]>
Received: from dxmint.cern.ch by  nxoc01.cern.ch  (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
    id AA00627; Tue, 1 Jun 93 18:34:07 MET DST
Received: from mcsun.EU.net by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
    id AA28075; Tue, 1 Jun 1993 18:55:43 +0200
Received: from hplb.hpl.hp.com by mcsun.EU.net with SMTP
    id AA03410 (5.65b/CWI-2.220); Tue, 1 Jun 1993 18:55:31 +0200
Received: from dragget.hpl.hp.com by hplb.hpl.hp.com; Tue, 1 Jun 93 15:09:20 +0100
Received: by manuel.hpl.hp.com
    (16.6/15.6+ISC) id AA10274; Tue, 1 Jun 93 15:15:03 +0100
From: Dave_Raggett <[e-mail]>
Message-Id: <[e-mail]>
Subject: Re: RE dtd2.html
To: [e-mail]
Date: Tue, 1 Jun 93 15:15:01 BST
Cc: [e-mail], [e-mail], [e-mail]
Mailer: Elm [revision: 66.36.1.1]

> I agree that flyleaf sounds like a bad idea.  In fact,
> Dave's navigational steps that lead to choosing a book
> in a bookstore is not a good guide to describing the
> logical structure of the information.  As Tim says,
> Summary or Abstract describes adequately what the information
> means; how it used or arranged are aspects of application,
> whether defined in the app interface, style sheet or user's
> navigational actions.

Thanks for the comments everyone. I am now considering how
to represent the structure in a more abstract manner using
attributes to carry has-part, has-property information.
This would allow generic markup to support evolving structures
for books, magazines and cyber-docs!

Thanks in particular to Tim for pointing me in this direction.
I hope to come back with some more details soon.

Best wishes,

Dave Raggett